Skip to content

Command messages - #1535

Merged
vietj merged 6 commits into
masterfrom
command-messages
Jul 2, 2025
Merged

Command messages#1535
vietj merged 6 commits into
masterfrom
command-messages

Conversation

@vietj

@vietj vietj commented Jul 2, 2025

Copy link
Copy Markdown
Member

CommandMessage are named XXXCodec due to the original design.

We should name those classes XXXCommandMessage instead to implement a more idiomatic design.

This rename the hierarchies for the implemented codecs.

In addition we try to avoid command message completion handler leaking into each codec and instead we keep this confined in the database socket connection.

@vietj vietj added this to the 5.1.0 milestone Jul 2, 2025
…ge and the associated flow.

Motivation:

Currently each codec takes care of failing the inflight command messages when a failure occurs in the pipeline. The socket connection already takes care of translating command responses to completion of the command handler.

We should let the socket connection take care of handling the case of failure, this avoids propagating the command response handler to each codec and the codec only cares about writing an inbound command response message.
@vietj
vietj force-pushed the command-messages branch from dfb20f6 to c684c42 Compare July 2, 2025 14:01
@vietj
vietj marked this pull request as ready for review July 2, 2025 14:05
@vietj
vietj merged commit 6a42909 into master Jul 2, 2025
18 checks passed
@vietj
vietj deleted the command-messages branch July 2, 2025 14:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant